Motivation

When planning function components, we missed a couple cases:

• when you want to forward a ref to a function component
• when you want to forward a ref using something than the existing component's props (way less common / important to solve)
  Example: https://reactjs.org/docs/forwarding-refs.html#forwarding-refs-to-dom-components

Changes

API Changes:

• Add uiForwardRef
• Update ref example to include different syntax examples
• Refactor forwardRef tests to be able to share test coverage with uiForwardRef
• Add uiForwardRef tests

Builder Changes:

• Rename FunctionComponentConfig to UiFactoryConfig
• Rename / refactor isFunctionComponentFactory to shouldGenerateConfig
• Create a getter on Identifier that can be used to check if the name is a factory type
• Switch out a couple checks on the identifier name with checks for the presence of a generated UiFactoryConfig

Release Notes

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
    • QA that the refs print correctly in the example. Note that the components do have code around logging, but that's to keep some consistency between React's docs and our examples. Because there aren't any props updated, there isn't any re-rendering and no reason for the components to log.
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Client Platform member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct